Pin llama.cpp b9986; make the b9977→b9978 patch-0005-obsoleting commit explicit#340
Merged
bernardladenthin merged 4 commits intoJul 13, 2026
Merged
Conversation
The b9975-b9981 history row attributed the server-context.cpp checkpoint rework to the whole range. Per-sub-tag diffing shows it landed at a single commit, b9977->b9978; the other steps in the range either touch no patch-target file or touch a different function in a patch-target file.
…ry rows Additive-only bump (SYCL backend internals + auto-followed WebUI only, no patch-target file touched); all six remaining patches apply unchanged. Full native build + ctest: 485/485 passing. Also recovers the b9981-b9982 history-doc rows from orphaned commit 6eacc95, which never made it into main - PR #339 appears to have been merged at an earlier commit on that branch before the follow-up commit landed.
Additive-only bump (SYCL topk-moe kernels + NVIDIA-Nemotron auto-parser tuning + auto-followed WebUI only, no patch-target file touched). A fresh native build + full ctest run is in progress to confirm the remaining patches still apply and compile cleanly against b9986; results will follow in a subsequent commit.
Append the b9984-b9986 history rows: SYCL topk-moe kernels and an NVIDIA-Nemotron auto-parser whitespace fix, no patch-target file touched. This is the final chunk of the b9982->b9986 bump - all six remaining patches (0001-0003, 0006-0008) apply cleanly.
bernardladenthin
had a problem deploying
to
maven-central
July 13, 2026 12:49 — with 
GitHub Actions
Failure
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
startgate
July 13, 2026 12:49 — with
GitHub Actions
Error
GitHub Actions
Error
bernardladenthin
had a problem deploying
to
maven-central
July 13, 2026 12:49 — with
GitHub Actions
Failure
GitHub Actions
Failure
|
bernardladenthin
deleted the
claude/precise-b9978-checkpoint-obsoletes-0005
branch
July 13, 2026 12:59
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
patches/target file or priority-8 header touched, so all six carried patches (0001–0003,0006–0008) still apply unchanged.docs/history/llama-cpp-breaking-changes.mdb9975–b9981 entry to pin the exact sub-tag (b9977→b9978) that made patch0005obsolete, instead of attributing it to the whole range.Test plan
cmake -B build+ fullcmake --build+ctestat both b9984 and b9986: 485/485 passing each timePATCH_COMMANDconfirms all six patches apply cleanly at each pinned tagRelated issues / PRs
Follow-up to #339 (b9975 → b9982 bump).
Checklist
Generated by Claude Code